home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
comm
/
commodsz.zip
/
COMMODSZ.DOC
< prev
next >
Wrap
Text File
|
1989-07-14
|
10KB
|
208 lines
This is a no frills collection of scripts, .DVPs, and a batch file
intended to provide an example of a way to exploit the DV environment.
In other words, use this stuff at your own risk - I'm only trying to
help, but if you muck something up, it AIN'T my fault!!!!
Anyway, to get to the good stuff: I call this knowledge sharing.
No shareware - no requests for cash. We've all spent enough as it is.
On the other hand, to get any use out of this, you WILL need the following
shareware products:
COMMO310.ZIP - by Fred P. Brucker
DSZ.ZIP - from Omen Technologies
STKEY2.ZIP - Richard M. Wilson/Barry Simon
With all that said......
***********************************************
Let's Have FUN!!!!!!!
***********************************************
Contained in this archive are the following files:
DESQVIEW.DVS - 'Main' Scripts for DV
DESQVIEW.TXT - 'Main' Scripts for DV in text form
CO-SCRIP.DVS - Scripts for COMMO310.ZIP
DSZDV.BAT - A batch file for the startup of the
DSZ partition.
CO-PIF.DVP - An example PIF for {COMMO}
ZZ-PIF.DVP - ditto for DSZ
If you've gotten impatient and already ADDed A PROGRAM on these two
DVPs, you've probably already noticed that the memory requirements are
set at 65K - and here's where the fun begins! Yes, I'm suggesting
that it's possible to have functional communications in all of 65K.
If you've got a 386 with umpteen Megs of RAM, then you don't need this.
However, 286 owners (like me) might appreciate it a great deal.
I used to use ProCOMM Plus TD, that is until I found {COMMO} and discovered
that it's just as useful, if not more so, than PCP. Not only that, it's a
30-odd K pgm, and comes equipped with a 100K .DVP spec that works just dandy
as well as macros that give you all the interfaces to DSZ that you need.
But even with the macros, you've still got the overhead of that 30K of
temporarily useless code during file transfers, and this collection of
files is intended to alleviate that situation. Fact is, when you've got
a protocol driver in charge of your modem, your telecom package is just
useless, dead memory. So - these scripts along with DSZDV.BAT install the
following functions:
From CO: PF12 is a 'dummy' script that taps the DESQ key and
and hits ^End on the numeric keypad. This initiates
a main DV script that first keys an ALT-X into the
CO window, then opens the ZZ window and passes a parameter
of 'rz' to DSZDV.BAT to pass to DSZ.
PF11 performs an identical task with ^Down, except it
keys 'sz' (assuming a UL), then goes into variable pause.
Key in your filenames, or backspace over sz and key
what you like - what you enter is passed to DSZ unchanged.
(i.e. 'sz filespec' for upload, 'rc' for XModem CRC
receive, 't' for DSZ talk, etc.) See your DSZ docs for
more information)
At this point (with luck), you'll have exited {COMMO} (thus freeing up its 65k),
and begun (in the same 65K) the DSZDV.BAT batch file. The basic functions of
DSZDV.BAT are:
1) An execution of STACKEY to hit the DESQ key and hide the pgm
(bypassed if 't' is passed to the batch file for DSZ talk)
The desired effect is for the DSZ window to pop up only
briefly, then disappear and do its stuff in the background.
It'll let you know when it's done. One note, however: I've
discovered that STACKEY ! X38FF will pop up the script Learn
menu. I've also discovered that if you do this in DV (or
anything like it (X38Fn), you're likely to knock things all
out of whack. At the very least, you'll make this call to
put DSZ in the background ineffective (and the BG.COM pgm that
I tried out didn't seem to fare much better). To play it safe,
either don't use STACKEY to manipulate the DV keyboard in any
way other than X38FC for the main menu, or live with the
inconvenience of having to put DSZ in the background manually.
What you see here: DV in action for a second or two, then
you're left to work in your other partitions until DSZ is done.
2) Startup of DVANSI.COM if 't' was the parm, plus a STACKEY zoom
of the DSZ window, and a carriage return to get the DSZ talk
session moving along.
3) Execution of DSZ to do whatever
4) A little music courtesy of STACKEY to let you know DSZ is done
5) Another STACKEY call to tap the DESQ key and hit Alt-0. This
key is configured in the DESQVIEW.DVS file to pause for a
second to let DVSDV.BAT finish (on slower machines, you might
want to up the delay to 2 - I don't really know for sure), then
it opens the CO window again (into the same 65K), hits
the ESC key to bypass modem initialization, and does
a carriage return (as some BBS systems seem to want one after
a file transfer)
What you see here: After the music (removable, of course, by
editing the batch file), the DESQ menu will pop up into your
current window, hold there a second, then {COMMO} will open
and you're ready to roll.
A few additional notes:
You will, of course, need to edit DSZDV.BAT and the DVPs to
conform to your directory/path structure. And if you have any
scripts in DESQVIEW.DVS, you need to run CONVSCR against your
script file, concatenate the contained DESQVIEW.TXT scripts
to it with an editor, make sure I'm not overlaying any of your
own scripts, and convert it back to .DVS format with CONVSCR.
Important stuff:
* Change ZZ-PIF.DVP to point to the directory where you
keep your Upload/Download files.
* Be sure to edit the 'port' parameter on the DSZ statement in
in DVDSZ.BAT to your com port. It's set at 2.
* Once you get the ZZ window to come up, if you still have
problems, make the STACKEY ! X38FC "rh" line a comment in
DSZDV.BAT so you can watch what happens (if you've made it
this far, your problem's probably either in DSZDV.BAT, or the
directory specified in the DVP - use CP to to check)
65K is not the minimum you can achieve with this technique. DSZ
will run in less (63K even with the batch file, and less than that
without DVANSI). This config is designed to be comfortable, and
though it's not mentioned above, I also load DVANSI into the
CO window as the ANSI graphics translation without it seem a bit
shakier in the COMMO310 release (though it does work). Feel free
to tweak the memory specs all you want, the important thing is
that memory usage in the two DVPs be IDENTICAL (this includes the
script buffer and the text/graphics pages), otherwise in a full
system, one of the windows won't successfully open.
The script linkage that allows all this to happen is not restricted
to {COMMO} and will work with any comm package - I used to do it
with PCP so I could use DSZ with no overhead - {COMMO} is
mentioned here because it's small (what other comm package needs
so little memory?) and very functional. If you're addicted to
something else, you can modify the scripts to your liking - at
the very least you'll be able to use ZMODEM